[Snyk] Fix for 2 vulnerabilities#5583
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300775 - https://snyk.io/vuln/SNYK-JS-WEBPACKDEVSERVER-10300777
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideThis PR replaces workspace references for @backstage/errors and @backstage/types in the config-loader package.json with explicit version 0.1.1 pins to remediate two Snyk-reported webpack-dev-server vulnerabilities. Flow Diagram: PR Merge Steps for yarn.lockgraph TD
A[Review PR Changes] --> B{yarn.lock updated by PR?};
B -- "No (Warning in PR)" --> C[Manually update yarn.lock];
C --> D[Merge PR];
B -- "Yes" --> D;
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
| "@backstage/errors": "0.1.1", | ||
| "@backstage/types": "0.1.1", |
There was a problem hiding this comment.
This change replaces workspace references with fixed version dependencies, which breaks the monorepo's dependency management system. In a monorepo, workspace:^ ensures packages use local versions during development, maintaining consistency across the codebase.
Fixed versions (0.1.1) will pull from npm instead of using local code, potentially causing:
- Version mismatches between packages
- Difficulty testing local changes across packages
- Inconsistent behavior between development and production
To properly address the webpack-dev-server vulnerabilities while maintaining monorepo integrity:
- Update the vulnerable dependencies in their source packages
- Keep the
workspace:^references intact - Update the root package.json or yarn.lock with the patched versions
This ensures the security fixes propagate through the workspace references while preserving the monorepo structure.
| "@backstage/errors": "0.1.1", | |
| "@backstage/types": "0.1.1", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/types": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
⛔ Snyk checks have failed. 2 issues have been found so far.
⛔ security/snyk check is complete. 2 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
packages/config-loader/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-WEBPACKDEVSERVER-10300775
SNYK-JS-WEBPACKDEVSERVER-10300777
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.
Summary by Sourcery
Bug Fixes: